Mobile device and control method thereof

ABSTRACT

This specification relates to a mobile terminal capable of executing a lock state of restricting a touch input and a control method thereof. The control method for the mobile terminal, which displays a lock screen in the lock state of restricting an input of a control command for an application, includes displaying an execution screen of an application on the lock screen, and controlling the lock screen based upon a touch input detected in the lock state.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.14/466,618, filed on Aug. 22, 2014, now U.S. Pat. No. 9,137,669, whichis a continuation of U.S. application Ser. No. 13/279,125, filed on Oct.21, 2011, now U.S. Pat. No. 8,850,560, which claims the benefit ofearlier filing date and right of priority to Korean Patent ApplicationNo. 10-2011-0043165, filed on May 6, 2011, the contents of which are allhereby incorporated by reference herein in their entirety.

BACKGROUND OF THE INVENTION 1. Field of the Invention

This specification relates to a mobile device capable of supporting atouch input and a control method thereof.

2. Background of the Invention

Mobile device (mobile terminal, portable device, portable terminal) canbe easily carried and have one or more of functions such as supportingvoice and video telephony calls, inputting and/or outputtinginformation, storing data and the like.

As it becomes multifunctional, the mobile terminal can be allowed tocapture still images or moving images, play music or video files, playgames, receive broadcast and the like, so as to be implemented as anintegrated multimedia player.

Various new attempts have been made for the multimedia devices byhardware or software in order to implement such complicated functions.

Furthermore, many efforts are undergoing to support or enhance variousfunctions of such mobile terminals. Such many efforts include not onlychanges and improvement of structural components implementing a mobileterminal but also software or hardware improvement.

When a user inputs a control command through a touch screen, the mobileterminal executes a lock mode (state) for restricting the user frominputting a control command in order to prevent an unexpected touchinput. Also, in the lock mode, a lock screen including information suchas date, time and the like is displayed.

SUMMARY OF THE INVENTION

Therefore, an aspect of the detailed description is to provideinformation related to an application on a lock screen of a mobiledevice (mobile terminal, portable terminal).

Another aspect of the detailed description is to provide a mobileterminal capable of easily accessing an application when a lock state isreleased.

To achieve these and other advantages and in accordance with the purposeof this specification, as embodied and broadly described herein, amethod for controlling a mobile terminal, which displays a lock screenin a lock state of restricting an input of a control command for anapplication, may include displaying an execution screen of anapplication on the lock screen, and controlling the lock screen basedupon a touch input detected in the lock state.

The controlling of the lock screen may be configured to convert thedisplayed execution screen into an execution screen of anotherapplication based upon the touch input.

The lock screen may display one of execution screens of a plurality ofapplications which are being run in the lock state, and when the touchinput is detected, the displayed execution screen may be disappeared andanother execution screen of the execution screens of the plurality ofapplications may be displayed, the another execution screen beingdifferent from the displayed execution screen.

The controlling of the lock screen may be configured to convert thedisplayed execution screen into an execution screen of anotherapplication or to activate an application corresponding to the displayedexecution screen and release the lock state, based upon different touchinputs.

When a first touch input is detected on the lock screen, the displayedexecution screen may be converted into the execution screen of theanother application, and when a second touch input consecutive to thefirst touch input is detected on the lock screen, the applicationcorresponding to the execution screen may be activated and the lockstate may be released.

The execution screen may be updated in the lock state according to anexecution of the application.

The lock screen may be kept powered on for a preset time, and thepower-on time of the lock screen may be set by inclination of the mobileterminal or by a key input.

The displaying of the execution screen of the application may beconfigured to display execution screens corresponding to a plurality ofapplications.

When a touch input is detected on one of the execution screens, anapplication corresponding to the one execution screen may be activatedand the lock state may be released.

The activated application may be an application corresponding to anexecution screen displayed at a portion where the touch input isreleased.

When a first touch input is detected on one of the execution screens, anobject as a target of a second touch input may be displayed, and whenthe second touch input is detected on the object, an applicationcorresponding to the one execution screen may be activated and the lockstate may be released.

When the application is an image capturing application, an image signalinput via a camera may be displayed on the execution screen.

The lock screen may display a control window for controlling capturingof the image signal.

When the application is a video reproducing application and the lockstate is executed, the video reproducing may be paused, and when thelock state is released, the video may be reproduced again.

The displayed execution screen in the lock state may be at least one ofan execution screen of an application last displayed before the lockstate is executed, an execution screen of an application having receiveda capture command before the lock state is executed, an execution screenof an application being executed in the lock state, or an executionscreen of an application having a newly generated event in the lockstate.

The displaying of the execution screen may be configured topreferentially display an execution screen of an application, from whichthe event has been generated during the lock state, over the otherexecution screens.

The method may further include executing the lock state in a state thatthe execution screen of the application has been captured, and theexecution screen displayed on the lock screen may be the capturedexecution screen of the application.

In accordance with one exemplary embodiment, a mobile terminal fordisplaying a lock screen in a lock state of restricting an input of acontrol command for an application may include a display unit configuredto display an execution screen of the application on the lock screen, atouch controller configured to detect a touch input applied onto thedisplay unit in the lock state, and a controller configured to controlthe lock screen based upon the detected touch input.

The controller may be configured to convert the displayed executionscreen into an execution screen of another application based upon thedetected touch input.

The controller may be configured to convert the displayed executionscreen into an execution screen of another application or activate anapplication corresponding to the displayed execution screen and releasethe lock state, based upon different touch inputs.

The display unit may display execution screens corresponding to aplurality of applications, and when the touch controller detects a firsttouch input on one of the execution screens, the display unit maydisplay an object as a target of a second touch input.

When the second touch input is detected on the object, the controllermay activate an application corresponding to the one execution screenand release the lock state.

Further scope of applicability of the present application will becomemore apparent from the detailed description given hereinafter. However,it should be understood that the detailed description and specificexamples, while indicating preferred embodiments of the invention, aregiven by way of illustration only, since various changes andmodifications within the spirit and scope of the invention will becomeapparent to those skilled in the art from the detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this specification, illustrate exemplary embodiments andtogether with the description serve to explain the principles of theinvention.

In the drawings:

FIG. 1 is a block diagram of a mobile terminal in accordance with oneexemplary embodiment;

FIG. 2A is a front perspective view of the mobile terminal;

FIG. 2B is a rear perspective view of the mobile terminal;

FIG. 3 is a flowchart showing a control method for the mobile terminal;

FIGS. 4A, 4B, 4C and 4D are overviews of a lock screen displayed in alock state of the mobile terminal;

FIGS. 5A and 5B are overviews of the lock screen displayed in the lockstate of the mobile terminal;

FIGS. 6A and 6B are overviews showing a method for shifting the lockscreen displayed in the lock state of the mobile terminal;

FIGS. 7A and 7B are overviews showing a method for shifting the lockscreen displayed in the lock state of the mobile terminal;

FIGS. 8, 9A, 9B, 10A and 10B are overviews showing a method forexecuting an application in the lock state of the mobile terminal;

FIG. 11 is an overview showing a method for shifting the lock screen orexecuting an application in the mobile terminal;

FIGS. 12 and 13 are overviews showing one exemplary embodiment of amethod for controlling the lock screen of the mobile terminal;

FIGS. 14A, 14B, 15A and 15B are overviews showing another exemplaryembodiment of the method for controlling the lock screen of the mobileterminal; and

FIG. 16 is an overview showing a method for displaying a captured screenas a lock screen in the mobile terminal.

DETAILED DESCRIPTION OF THE INVENTION

Description will now be given in detail of the exemplary embodiments,with reference to the accompanying drawings. For the sake of briefdescription with reference to the drawings, the same or equivalentcomponents will be provided with the same reference numbers, anddescription thereof will not be repeated. Hereinafter, suffixes “module”and “unit or portion” for components used herein in description aremerely provided only for facilitation of preparing this specification,and thus they are not granted a specific meaning or function. Indescribing the present invention, if a detailed explanation for arelated known function or construction is considered to unnecessarilydivert the gist of the present disclosure, such explanation has beenomitted but would be understood by those skilled in the art. Theaccompanying drawings are used to help easily understood the technicalidea of the present invention and it should be understood that the ideaof the present disclosure is not limited by the accompanying drawings.

Mobile terminals described in this specification may include cellularphones, smart phones, laptop computers, digital broadcasting terminals,personal digital assistants (PDAs), portable multimedia players (PMPs),E-books, navigators, and the like. However, it may be easily understoodby those skilled in the art that the configuration according to theexemplary embodiments of this specification can be applied to stationaryterminals such as digital TV, desktop computers and the like excluding acase of being applicable only to the mobile terminals.

FIG. 1 is a block diagram of a mobile terminal 100 in accordance withone exemplary embodiment.

The mobile terminal 100 may comprise components, such as a wirelesscommunication unit 110, an Audio/Video (A/V) input unit 120, a userinput unit 130, a sensing unit 140, an output unit 150, a memory 160, aninterface unit 170, a controller 180, a power supply 190 and the like.FIG. 1 shows the mobile terminal 100 having various components, but itis understood that implementing all of the illustrated components is nota requirement. Greater or fewer components may alternatively beimplemented.

Hereinafter, each component is described in sequence.

The wireless communication unit 110 may typically include one or moremodules which permit wireless communications between the mobile terminal100 and a wireless communication system or between the mobile terminal100 and a network within which the mobile terminal 100 is located. Forexample, the wireless communication unit 110 may include a broadcastreceiving module 111, a mobile communication module 112, a wirelessInternet module 113, a short-range communication module 114, a locationinformation module 115 and the like.

The broadcast receiving module 111 receives a broadcast signal and/orbroadcast associated information from an external broadcast managingentity via a broadcast channel.

The broadcast channel may include a satellite channel and a terrestrialchannel. The broadcast managing entity may indicate a server whichgenerates and transmits a broadcast signal and/or broadcast associatedinformation or a server which receives a pre-generated broadcast signaland/or broadcast associated information and sends them to the mobileterminal. The broadcast signal may be implemented as a TV broadcastsignal, a radio broadcast signal, and a data broadcast signal, amongothers. The broadcast signal may further include a data broadcast signalcombined with a TV or radio broadcast signal.

Examples of broadcast associated information may include informationassociated with a broadcast channel, a broadcast program, a broadcastservice provider, and the like. The broadcast associated information maybe provided via a mobile communication network, and received by themobile communication module 112.

The broadcast associated information may be implemented in variousformats. For instance, broadcast associated information may includeElectronic Program Guide (EPG) of Digital Multimedia Broadcasting (DMB),Electronic Service Guide (ESG) of Digital Video Broadcast-Handheld(DVB-H), and the like.

The broadcast receiving module 111 may be configured to receive digitalbroadcast signals transmitted from various types of broadcast systems.Such broadcast systems may include Digital MultimediaBroadcasting-Terrestrial (DMB-T), Digital MultimediaBroadcasting-Satellite (DMB-S), Media Forward Link Only (MediaFLO),Digital Video Broadcast-Handheld (DVB-H), Integrated Services DigitalBroadcast-Terrestrial (ISDB-T) and the like. The broadcast receivingmodule 111 may be configured to be suitable for every broadcast systemtransmitting broadcast signals as well as the digital broadcastingsystems.

Broadcast signals and/or broadcast associated information received viathe broadcast receiving module 111 may be stored in a suitable device,such as a memory 160.

The mobile communication module 112 transmits/receives wireless signalsto/from at least one of network entities (e.g., base station, anexternal mobile terminal, a server, etc.) on a mobile communicationnetwork. Here, the wireless signals may include audio call signal, video(telephony) call signal, or various formats of data according totransmission/reception of text/multimedia messages.

The mobile communication module 112 may implement a video call mode anda voice call mode. The video call mode indicates a state of calling withwatching a callee's image. The voice call mode indicates a state ofcalling without watching the callee's image. The wireless communicationmodule 112 may transmit and receive at least one of voice and image inorder to implement the video call mode and the voice call mode.

The wireless Internet module 113 supports wireless Internet access forthe mobile terminal. This module may be internally or externally coupledto the mobile terminal 100. Examples of such wireless Internet accessmay include Wireless LAN (WLAN) (Wi-Fi), Wireless Broadband (Wibro),Worldwide Interoperability for Microwave Access (Wimax), High SpeedDownlink Packet Access (HSDPA) and the like.

The short-range communication module 114 denotes a module forshort-range communications. Suitable technologies for implementing thismodule may include BLUETOOTH™, Radio Frequency IDentification (RFID),Infrared Data Association (IrDA), Ultra-WideBand (UWB), ZigBee™, and thelike.

The location information module 115 denotes a module for detecting orcalculating a position of a mobile terminal. An example of the locationinformation module 115 may include a Global Position System (GPS)module.

Referring to FIG. 1, the A/V input unit 120 is configured to provideaudio or video signal input to the mobile terminal. The A/V input unit120 may include a camera 121 and a microphone 122. The camera 121receives and processes image frames of still pictures or video obtainedby image sensors in a video call mode or a capturing mode. The processedimage frames may be displayed on a display unit 151.

The image frames processed by the camera 121 may be stored in the memory160 or transmitted to the exterior via the wireless communication unit110. Two or more cameras 121 may be provided according to theconfiguration of the mobile terminal.

The microphone 122 may receive an external audio signal while the mobileterminal is in a particular mode, such as a phone call mode, a recordingmode, a voice recognition mode, or the like. This audio signal isprocessed into digital data. The processed digital data is converted foroutput into a format transmittable to a mobile communication basestation via the mobile communication module 112 in case of the phonecall mode. The microphone 122 may include assorted noise removingalgorithms to remove noise generated in the course of receiving theexternal audio signal.

The user input unit 130 may generate input data input by a user tocontrol the operation of the mobile terminal. The user input unit 130may include a keypad, a dome switch, a touchpad (e.g., staticpressure/capacitance), a jog wheel, a jog switch and the like.

The sensing unit 140 provides status measurements of various aspects ofthe mobile terminal. For instance, the sensing unit 140 may detect anopen/close status of the mobile terminal, a change in a location of themobile terminal 100, a presence or absence of user contact with themobile terminal 100, the location of the mobile terminal 100,acceleration/deceleration of the mobile terminal 100, and the like, soas to generate a sensing signal for controlling the operation of themobile terminal 100. For example, regarding a slide-type mobileterminal, the sensing unit 140 may sense whether a sliding portion ofthe mobile terminal is open or closed. Other examples include sensingfunctions, such as the sensing unit 140 sensing the presence or absenceof power provided by the power supply 190, the presence or absence of acoupling or other connection between the interface unit 170 and anexternal device.

The output unit 150 is configured to output an audio signal, a videosignal or a tactile signal. The output unit 150 may include a displayunit 151, an audio output module 152, an alarm unit 153 and a hapticmodule 154.

The display unit 151 may output information processed in the mobileterminal 100. For example, when the mobile terminal is operating in aphone call mode, the display unit 151 will provide a User Interface (UI)or a Graphic User Interface (GUI), which includes information associatedwith the call. As another example, if the mobile terminal is in a videocall mode or a capturing mode, the display unit 151 may additionally oralternatively display images captured and/or received, UI, or GUI.

The display unit 151 may be implemented using, for example, at least oneof a Liquid Crystal Display (LCD), a Thin Film Transistor-Liquid CrystalDisplay (TFT-LCD), an Organic Light-Emitting Diode (OLED), a flexibledisplay, a three-dimensional (3D) display, an e-ink display or the like.

Some of such displays 151 may be implemented as a transparent type or anoptical transparent type through which the exterior is visible, which isreferred to as ‘transparent display’. A representative example of thetransparent display may include a Transparent OLED (TOLED), and thelike. The rear surface of the display unit 151 may also be implementedto be optically transparent. Under this configuration, a user can viewan object positioned at a rear side of a terminal body through a regionoccupied by the display unit 151 of the terminal body.

The display unit 151 may be implemented in two or more in numberaccording to a configured aspect of the mobile terminal 100. Forinstance, a plurality of the displays 151 may be arranged on one surfaceto be spaced apart from or integrated with each other, or may bearranged on different surfaces.

Here, if the display unit 151 and a touch sensitive sensor (referred toas a touch sensor) have a layered structure therebetween, the structuremay be referred to as a touch screen. The display unit 151 may be usedas an input device rather than an output device. The touch sensor may beimplemented as a touch film, a touch sheet, a touchpad, and the like.

The touch sensor may be configured to convert changes of a pressureapplied to a specific part of the display unit 151, or a capacitanceoccurring from a specific part of the display unit 151, into electricinput signals. Also, the touch sensor may be configured to sense notonly a touched position and a touched area, but also a touch pressure.

When touch inputs are sensed by the touch sensors, corresponding signalsare transmitted to a touch controller (not shown). The touch controllerprocesses the received signals, and then transmits corresponding data tothe controller 180. Accordingly, the controller 180 may sense whichregion of the display unit 151 has been touched.

Still referring to FIG. 1, a proximity sensor 141 may be arranged at aninner region of the mobile terminal 100 covered by the touch screen, ornear the touch screen. The proximity sensor 141 indicates a sensor tosense presence or absence of an object approaching to a surface to besensed, or an object disposed near a surface to be sensed, by using anelectromagnetic field or infrared rays without a mechanical contact. Theproximity sensor 141 has a longer lifespan and a more enhanced utilitythan a contact sensor.

The proximity sensor 141 may include a transmissive type photoelectricsensor, a direct reflective type photoelectric sensor, a mirrorreflective type photoelectric sensor, a high-frequency oscillationproximity sensor, a capacitance type proximity sensor, a magnetic typeproximity sensor, an infrared rays proximity sensor, and so on. When thetouch screen is implemented as a capacitance type, proximity of apointer to the touch screen is sensed by changes of an electromagneticfield. In this case, the touch screen (touch sensor) may be categorizedinto a proximity sensor.

Hereinafter, for the sake of brief explanation, a status that thepointer is positioned to be proximate onto the touch screen withoutcontact will be referred to as ‘proximity touch’, whereas a status thatthe pointer substantially comes in contact with the touch screen will bereferred to as ‘contact touch’. For the position corresponding to theproximity touch of the pointer on the touch screen, such positioncorresponds to a position where the pointer faces perpendicular to thetouch screen upon the proximity touch of the pointer.

The proximity sensor 141 senses proximity touch, and proximity touchpatterns (e.g., distance, direction, speed, time, position, movingstatus, etc.). Information relating to the sensed proximity touch andthe sensed proximity touch patterns may be output onto the touch screen.

The audio output module 152 may output audio data received from thewireless communication unit 110 or stored in the memory 160, in acall-receiving mode, a call-placing mode, a recording mode, a voicerecognition mode, a broadcast reception mode, and so on. The audiooutput module 152 may output audio signals relating to functionsperformed in the mobile terminal 100, e.g., sound alarming a callreceived or a message received, and so on. The audio output module 152may include a receiver, a speaker, a buzzer, and so on.

The alarm unit 153 outputs signals notifying occurrence of events fromthe mobile terminal 100. The events occurring from the mobile terminal100 may include call received, message received, key signal input, touchinput, and so on. The alarm unit 153 may output not only video or audiosignals, but also other types of signals such as signals notifyingoccurrence of events in a vibration manner. Since the video or audiosignals can be output through the display unit 151 or the audio outputmodule 152, the display unit 151 and the audio output module 152 may becategorized into a part of the alarm unit 153.

The haptic module 154 generates various tactile effects which a user canfeel. A representative example of the tactile effects generated by thehaptic module 154 includes vibration. Vibration generated by the hapticmodule 154 may have a controllable intensity, a controllable pattern,and so on. For instance, different vibration may be output in asynthesized manner or in a sequential manner.

The haptic module 154 may generate various tactile effects, includingnot only vibration, but also arrangement of pins vertically moving withrespect to a skin being touched (contacted), air injection force or airsuction force through an injection hole or a suction hole, touch by askin surface, presence or absence of contact with an electrode, effectsby stimulus such as an electrostatic force, reproduction of cold or hotfeeling using a heat absorbing device or a heat emitting device, and thelike.

The haptic module 154 may be configured to transmit tactile effects(signals) through a user's direct contact, or a user's muscular senseusing a finger or a hand. The haptic module 154 may be implemented intwo or more in number according to the configuration of the mobileterminal 100.

The memory 160 may store a program for the processing and control of thecontroller 180. Alternatively, the memory 160 may temporarily storeinput/output data (e.g., phonebook data, messages, still images, videoand the like). Also, the memory 160 may store data related to variouspatterns of vibrations and audio output upon the touch input on thetouch screen.

The memory 160 may be implemented using any type of suitable storagemedium including a flash memory type, a hard disk type, a multimediacard micro type, a memory card type (e.g., SD or DX memory), RandomAccess Memory (RAM), Static Random Access Memory (SRAM), Read-OnlyMemory (ROM), Electrically Erasable Programmable Read-Only Memory(EEPROM), Programmable Read-Only Memory (PROM), magnetic memory,magnetic disk, optical disk, and the like. Also, the mobile terminal 100may operate a web storage which performs the storage function of thememory 160 on the Internet.

The interface unit 170 may generally be implemented to interface themobile terminal with external devices. The interface unit 170 may allowa data reception from an external device, a power delivery to eachcomponent in the mobile terminal 100, or a data transmission from themobile terminal 100 to an external device. The interface unit 170 mayinclude, for example, wired/wireless headset ports, external chargerports, wired/wireless data ports, memory card ports, ports for couplingdevices having an identification module, audio Input/Output (I/O) ports,video I/O ports, earphone ports, and the like.

The identification module may be configured as a chip for storingvarious information required to authenticate an authority to use themobile terminal 100, which may include a User Identity Module (UIM), aSubscriber Identity Module (SIM), and the like. Also, the device havingthe identification module (hereinafter, referred to as ‘identificationdevice’) may be implemented in a type of smart card. Hence, theidentification device can be coupled to the mobile terminal 100 via aport.

Also, the interface unit 170 may serve as a path for power to besupplied from an external cradle to the mobile terminal 100 when themobile terminal 100 is connected to the external cradle or as a path fortransferring various command signals input from the cradle by a user tothe mobile terminal 100. Such various command signals or power inputfrom the cradle may operate as signals for recognizing that the mobileterminal 100 has accurately been mounted to the cradle.

The controller 180 typically controls the overall operations of themobile terminal 100. For example, the controller 180 performs thecontrol and processing associated with telephony calls, datacommunications, video calls, and the like. The controller 180 mayinclude a multimedia module 181 which provides multimedia playback. Themultimedia module 181 may be configured as part of the controller 180 oras a separate component.

The controller 180 can perform a pattern recognition processing so as torecognize writing or drawing input on the touch screen as text or image.

Also, the controller 180 may execute a lock state, in which a user isrestricted from inputting a control command for applications, when astate of the mobile terminal satisfies a preset condition. Thecontroller 180 may control a lock screen, which is displayed in the lockstate, based upon a touch input detected on the display unit 151(hereinafter, referred to ‘touch screen’) in the lock state.

The power supply 190 provides power required by various components underthe control of the controller 180. The provided power may be internalpower, external power, or combination thereof.

Various embodiments described herein may be implemented in acomputer-readable medium using, for example, software, hardware, or somecombination thereof.

For a hardware implementation, the embodiments described herein may beimplemented within one or more Application Specific Integrated Circuits(ASICs), Digital Signal Processors (DSPs), Digital Signal ProcessingDevices (DSPDs), Programmable Logic Devices (PLDs), Field ProgrammableGate Arrays (FPGAs), processors, microprocessors, other electronic unitsdesigned to perform the functions described herein, or a selectivecombination thereof. In some cases, such embodiments are implemented bythe controller 180.

For software implementation, the embodiments such as procedures andfunctions may be implemented together with separate software moduleseach of which performs at least one of functions and operations.

The software codes can be implemented with a software applicationwritten in any suitable programming language. Also, the software codesmay be stored in the memory 160 and executed by the controller 180.

Hereinafter, description will be given of the structure of the mobileterminal in accordance with the one exemplary embodiment or a portableterminal or mobile terminal having components disposed.

FIG. 2A is a front perspective view of the portable or mobile terminal,and FIG. 2B is a rear perspective view of the mobile terminal of FIG.2A.

A mobile terminal 100 disclosed herein has a bar type terminal body.Here, the present disclosure may not be limited to the type, but beapplicable to various types such as a slide type, a folder type, a swingtype, a swivel type and the like, having two or more bodies coupled tobe relatively movable with each other.

The terminal body 100 (hereinafter, referred to as ‘body’) includes afront surface, side surfaces and a rear surface. Also, the body includesboth ends formed in a lengthwise direction.

The body may include a case (casing, housing, cover, etc.) defining anouter appearance. In this exemplary embodiment, the case may be dividedinto a front surface (hereinafter, referred to as ‘front case’) 101 anda rear surface (referred to as ‘rear case’) 102. Various electroniccomponents may be mounted in a space between the front case 101 and therear case 102. At least one intermediate case may further be interposedbetween the front case 101 and the rear case 102.

Such cases may be injected using a synthetic resin or be formed of ametal, such as stainless steel (STS), titanium (Ti) or the like.

The terminal body is shown having a display unit 151, an audio outputmodule 152, a camera 121, a user input unit 130/131, 132, a microphone122, an interface unit 170, and the like.

The display unit 151 may occupy most of a main surface of the front case101. The audio output module 152 and the camera 121 may be disposed nearone of both end portions of the display unit 151, and the user inputunit 131 and the microphone 122 on the other end portion of the displayunit 151. The user input unit 132, the interface unit 170 and the likemay be disposed on side surfaces of the front and rear cases 101 and102. The microphone 122 may be disposed at the other end of the body100.

The user input unit 130 may be manipulated to allow inputting ofcommands for controlling operations of the mobile terminal 100, andinclude a plurality of first manipulation units 131, 132. The pluralityof manipulation units 131, 132 may be referred to as a manipulatingportion. Such manipulating portion can employ any tactile manner that auser can touch or tap for manipulation.

The first and second manipulation units 131, 132 may be set to allowinputting of various contents. For example, the first manipulation unit131 may be configured to input commands such as START, END, SCROLL orthe like, and the second manipulation unit 132 may be configured toinput commands, such as a volume adjustment of sounds output from theaudio output module 152, conversion of the display unit 151 into a touchrecognition mode, or the like.

Referring to FIG. 2B, a rear face of the terminal body, namely, the rearcase 102 may further be provided with a camera 121′. The camera 121′faces a direction which is opposite to a direction faced by the camera121, and may have different pixels from those of the camera 121.

For example, the camera 121 may operate with relatively lower pixels(lower resolution). Thus, the camera 121 may be useful when a user cancapture his face and send it to another party during a video call or thelike. On the other hand, the camera 121′ may operate with a relativelyhigher pixels (higher resolution) such that it can be useful for a userto obtain higher quality pictures for later use. The cameras 121 and121′ may be installed in the terminal body to be rotatable or popped up.

A flash 123 and a mirror 124 may additionally be disposed adjacent tothe camera 121′. The flash 123 operates in conjunction with the camera121′ when taking a picture using the camera 121′. The mirror 124 cancooperate with the camera 121′ to allow a user to photograph himself ina self-portrait mode.

An audio output module 152′ may further be disposed at a rear face ofthe terminal body. The audio output module 152′ can cooperate with theaudio output module 152 (see FIG. 2A) to provide stereo output. Also,the audio output module 152′ may be configured to operate as aspeakerphone.

A broadcast signal receiving antenna 116 may further be disposed at oneside of the terminal body in addition to an antenna for communications,for example. The antenna 116 configuring a part of the broadcastreceiving module 111 (see FIG. 1) may be retractable into the terminalbody.

A power supply unit 190 for supplying power to the mobile terminal 100may be mounted in the terminal body. The power supply unit 190 may bemounted in the terminal body or detachably coupled directly onto theoutside of the terminal body.

The rear case 102 may be further provided with a touchpad 134 fordetecting a touch input. Similar to the display unit 151, the touchpad135 may be implemented as a light-transmissive type. Here, if thedisplay unit 151 is configured to output visual information from bothsurfaces, the visual information can be recognized through the touchpad135. The information output from the both surfaces may all be controlledby the touchpad 135. Unlike to this, a display may further be mounted onthe touchpad 135 so as to configure a touch screen even on the rear case102.

The touchpad 135 may operate cooperative with the display unit 151 ofthe front case 101. The touchpad 135 may be disposed at a rear side ofthe display unit 151 in parallel to the display unit 151. The touchpad135 may have a size the same as or smaller than that of the display unit151.

This specification proposes displaying of an execution screen of anapplication on a lock screen, which is displayed in a lock state of amobile terminal (mobile device, portable terminal), and controlling ofthe lock screen based upon a touch input detected in the lock state.

Hereinafter, description will be given of a method for controlling alock screen displayed in a lock state of a mobile terminal withreference to FIGS. 1, 2A and 2B described above and FIG. 3.

FIG. 3 is a flowchart showing a control method for a mobile terminal inaccordance with one exemplary embodiment.

First, a control method for a mobile terminal in accordance with oneexemplary embodiment may include executing (initiating, starting,running) a lock state when the mobile terminal meets a preset conditionin an unlock state (S100), displaying an execution screen of anapplication on a lock screen displayed in the lock state (S110), andcontrolling the lock screen based upon a touch input detected in thelock state (S120).

The mobile terminal in accordance with the one exemplary embodiment maybe in ‘lock state’ and ‘unlock state’ according to whether or not a useris allowed to input a control command for the mobile terminal.

First, the lock state indicates a state of restricting a user frominputting control commands for applications present in the mobileterminal. This is generally intended for preventing activation ordeactivation of functions and applications of a mobile terminal having atouch screen 151 due to an input of control commands, which areunexpected by a user. Therefore, in the lock state, the user may berestricted from inputting a control command through the touch screen 151and the user input unit 130 within a preset range.

Meanwhile, the inputting of the control command may be restricted in thelock state but functions of the mobile terminal and operations ofapplications, which were being run before the lock state is executed,may be continuously maintained.

The unlock state indicates a state of allowing a user to input controlcommands for the mobile terminal. Therefore, in this unlock state,functions and applications of the mobile terminal may be activated ordeactivated according to control commands input by the user.

Herein, the lock state may be executed (started) when a user input withrespect to the touch screen 151 and other user input unit 130 disposedon the mobile terminal is not detected for a preset time. The presettime may change according to a user's setting.

In this specification, as aforesaid, a case of executing a lock statedue to no detection of a user input with respect to the mobile terminalfor a preset time or detection of an input with respect to a specifickey may be explained as ‘executing a lock state when a preset conditionis satisfied.’

In addition, the unlock state may be executed by a user input appliedonto the specific key in the lock state or a touch input detected on alock screen, which is displayed in the lock state.

Herein, an application corresponding to an execution screen displayed asthe lock screen may be an application, which has been last displayedprior to executing the lock state, or an application corresponding to ascreen captured by a user's capture command prior to executing the lockstate. Also, an application corresponding to an execution screendisplayed as the lock screen may be an application which is being run inthe lock state, or an application from which a new event has beengenerated in the lock state. An application corresponding to anexecution screen displayed as the lock screen may be an applicationwhich has been executed prior to the lock state executed.

Hereinafter, description will be given of several exemplary embodimentsfor the control method.

FIGS. 4A to 4D shows a lock screen displayed in the lock state of themobile terminal.

First, referring to FIG. 4A, an execution screen 210 of an applicationmay be displayed on a lock screen, which is displayed in the lock stateof the mobile terminal. For example, when a screen, which was lastdisplayed prior to executing the lock state of the mobile terminal, isan application related to navigation, ‘map’ as an execution screen ofthe application may be displayed on the lock screen.

Referring to FIGS. 4B and 4C, execution screens 220 to 225 correspondingto a plurality of applications may be displayed on the lock screen ofthe mobile terminal.

The execution screens displayed in the lock state, as shown in FIG. 4C,may be displayed with overlapping a lock screen 210, which is set as adefault in the mobile terminal.

The controller 180 (see FIG. 1) of the mobile terminal, as shown in FIG.4D, may update the execution screen 210 of the application displayed onthe lock screen as the application is run.

For example, it is assumed that the application is a navigationapplication. Referring to FIG. 4D, the controller 180 updates anexecution screen (for example, a map corresponding to the currentlocation) displayed on the lock screen, in response to movement of theterminal. The controller 180 then displays on the lock screen theupdated execution screen, namely, a screen showing a state that theterminal is moving.

The controller 180 may preferentially display, as shown in FIGS. 5A and5B, an execution screen of an application, from which a new event hasbeen generated in the lock state, over the execution screens of otherapplications.

Herein, the newly generated event may include a text message received inthe lock state, a message received via a messenger, a push message andthe like.

As shown in FIG. 5A, while an execution screen 210 of a navigationapplication is displayed as the lock screen, for example, if a textmessage is received, the controller 180 may display an execution screen211 relating to the text message, instead of the execution screen 210 ofthe navigation application. Alternatively, the controller 180 maydisplay the execution screen 211 relating to the text message in anoverlapping manner with the execution screen 210 of the navigationapplication.

Referring to FIG. 5B, the controller 180 may preferentially display theexecution screen 223 of an application, from which the new event hasbeen generated, over execution screens of a plurality of applications220, 221 and 222 displayed on the lock screen.

Therefore, the mobile terminal in accordance with the one exemplaryembodiment can provide the updated execution screen in response torunning of the application as well as the execution screens of theapplications on the lock screen, which is displayed in the lock state,accordingly, a user can be provided with information relating to theapplications even when the mobile terminal is not in an unlock state.

The controller 180 of the mobile terminal may control the lock screenbased upon a touch input, which is detected on the lock screendisplaying the execution screens of applications, namely, a touch inputdetected on a touch screen, in the lock state of the mobile terminal.

Hereinafter, description will be given of a method for controlling thelock screen based upon a user's touch input through the touch screen inthe lock state.

The method for controlling the lock screen displayed in the lock stateof the mobile terminal according to the one exemplary embodiment isshown in FIGS. 6A, 6B, 7A, 7B, 8, 9A, 9B, 10A, 10B and 11.

First, FIGS. 6A and 6B show a method for shifting (converting) the lockscreen based upon a touch input, which is detected in the lock state ofthe mobile terminal.

Referring to FIG. 6A, when a user applies a touch input in a certaindirection to the lock screen, on which an execution screen 210 of thefirst application is displayed, the controller 180 (see FIG. 1) maydisappear the execution screen 210 of the first application and displayan execution screen 211 of a second application based upon the touchinput detected on the lock screen. (The touch input detected on the lockscreen is a touch input detected on the touch screen 151)

Similarly, referring to FIG. 6B, when a user applies a touch input in acertain direction to the lock screen, on which execution screens 220,221 and 222 of first to third applications are displayed, the controller180 may disappear the execution screen 220 of the first application anddisplay an execution screen 223 of a fourth application based upon thetouch input detected on the lock screen.

In the meantime, the touch input applied to the lock screen in thecertain direction may be set by a user or a default setting of themobile terminal, and also the input may be carried out in variousdirections, such as horizontally, vertically, diagonally and the like.

In the lock state, the controller 180 may respond to a touch input withrespect to every portion on the touch screen 151 (see FIGS. 1 and 2), orto a touch input with respect to a specific portion.

Hence, when the controller 180 is allowed to respond only to a touchinput applied to the specific portion in the lock state, the controller180 may convert (shift) the lock screen, as shown in FIGS. 6A and 6B,only when detecting a touch input applied to the specific portion.

Next, FIGS. 7A and 7B shows a method for enlarging or highlightingexecution screens of applications displayed on the lock screen basedupon a touch input detected in the lock state of the mobile terminal.

First, referring to FIG. 7A, on the lock screen, on which executionscreens 220, 221 and 222 of first to third applications are displayed,for example, upon detecting a touch input with respect to the executionscreen 220 of the first application, the controller 180 may enlarge theexecution screen 220 of the first application.

Referring to FIG. 7B, upon detecting a touch input with respect to theexecution screen 220 of the first application, the controller 180 mayhighlight the execution screen 220 of the first application. Also, upondetecting a user's touch input with respect to the highlighted executionscreen 220 of the first application, the controller 180 may enlarge theexecution screen 220 of the first application.

FIGS. 8, 9A, 9B, 10A and 10B respectively show a method for executing anapplication corresponding to an execution screen displayed on the lockscreen based upon a touch input detected in the lock state of the mobileterminal.

The controller 180 of the mobile terminal according to the one exemplaryembodiment may execute an application corresponding to an executionscreen displayed on the lock screen based upon a touch input detected inthe lock state.

Referring to FIG. 8, upon detecting a touch input on the lock screen, onwhich the execution screen 210 of the first application, namely, thetouch screen 151 (see FIGS. 1 and 2), then the controller 180 may runthe application corresponding to the execution screen 210 and convert(shift) the lock state into an unlock state.

The controller 180 may display an object 230 to be touched on the lockscreen, and upon detecting a touch input with respect to the object 230,execute an application corresponding to the execution screen displayedon the lock screen.

Herein, the object 230 is a target to be touched to release the lockstate. Hence, the lock state may be released only when a touch inputapplied to the object 230 on the touch screen 151 is detected.

As shown in FIGS. 9A and 9B, upon detecting a first touch input appliedto execution screens 220, 221 and 222 of first to third applicationsdisplayed on the lock screen, the controller 180 may display an object230 which is appeared for a second touch input. Also, upon detecting thesecond touch input applied to the object 230, the controller 180 maydisplay the application corresponding to the execution screen, on whichthe first touch input has been detected, and shift the mobile terminalfrom the lock state into the unlock state.

FIG. 10 shows another exemplary embodiment of executing applicationscorresponding to execution screens displayed on the lock screen.

First, as shown in FIG. 10A, on the lock screen, on which executionscreens 220 to 225 of first to sixth applications are displayed, thecontroller 180 (see FIG. 1) may execute an application corresponding toan execution screen located at a portion where a touch input startingfrom a first reference point 240 of the touch screen 151 (see FIGS. 1and 2) is released.

Herein, the touch input may be made by sliding, dragging or flicking,starting from the first reference point.

Meanwhile, referring to FIG. 10B, the controller 180 may allow the lockscreen having the execution screens to overlap a cover image 250 inorder to provide a user with visual information relating to the touchinput.

Herein, the cover image 250 may be a transparent image overlapped by theexecution screens. The controller 180 may make the cover image 250invisible based upon a touch input starting from the first referencepoint 240. The cover image 250 may be displayed to render an area, fromthe first reference point 240 to a point where the user's touch input isdetected, distinguished from other area. Hence, with this configuration,the touch screen may be divided into a first area 250 a where a touchinput is detected, and a second area 250 b whether a touch input is notdetected. Also, the controller 180 may execute an applicationcorresponding to an execution screen located on a portion where thetouch input is released, and shift the lock state into the unlock state.

FIG. 11 shows a method for shifting (converting) the lock screen orexecuting an application corresponding to an execution screen displayedon the lock screen, based upon a touch input detected in the lock stateof the mobile terminal.

The controller 180 of the mobile terminal may shift the lock screen orexecute an application corresponding to an execution screen displayed onthe lock screen responsive to different touch inputs detected on thetouch screen.

The touch input may include touch inputs applied in various manners,such as long touch, double touch, flicking, dragging, sliding and thelike. Also, the controller 180 may control the mobile terminal toexecute different operations according to preset control commands inresponse to the touch input and a touch direction.

For example, referring to FIG. 11A, upon detecting a first touch inputin a first direction (for example, a horizontal direction), thecontroller 180 may switch the execution screen 210 of the firstapplication displayed on the lock screen into the execution screen 211of the second application.

Upon detecting a second touch input on the execution screen 211 in adirection (for example, a vertical direction) different from the firstdirection, the controller 180 may execute an application correspondingto the execution screen 211 displayed on the lock screen.

As such, the controller 180 of the mobile terminal according to the oneexemplary embodiment may control or set the mobile terminal to executedifferent operations in the lock state based upon different touchinputs.

FIGS. 12 to 14 show exemplary embodiments of a method for controllingthe mobile terminal on the lock screen of the mobile terminal.

First, the mobile terminal according to the one exemplary embodiment, asmentioned above, may be configured to control an application using theobject 230, which is touched to execute the application corresponding tothe execution screen 210 displayed on the lock screen. For example,referring to FIG. 12, upon detecting a touch input on the executionscreen 221 of the second application on the lock screen, on which theexecution screens 220 to 225 of the first to sixth applications aredisplayed, the controller 180 may display the object 230 on one area ofthe display unit or the lock screen. Here, the controller 180 maydisplay the object 230 by including virtual keys (or visual keys) 260,which are used (touched) to control the second application (for example,a music playback application).

Therefore, the user can control the second application even on the lockscreen using the visual keys 260 displayed on the object 230, and thecontroller 180 may control play music in the mobile terminal in responseto the user's control command.

FIG. 13 shows a method for controlling the lock screen when an imagecapturing application was being run before the lock state is executed inthe mobile terminal.

As shown in FIG. 13, when the lock state is executed while a usercaptures an image using the image capturing application, the controller180 (see FIG. 1) may display an image signal input via a camera on thelock screen.

The controller 180 may display the visual keys 260, by which the imagecapturing can be controlled, on the lock screen, and receive a controlcommand input by the user via the visual keys 260 so as to capture animage displayed on the lock screen. Also, the controller 180 may controlthe image captured in the lock state to be stored in a memory.

FIGS. 14A and 14B respectively show a method for controlling the lockscreen when a video reproducing application was being run before thelock state is executed in the mobile terminal.

Referring to FIG. 14A, while a video reproducing application is run inthe unlock state of the mobile terminal, when the lock state is executeddue to satisfaction of a preset condition, then the controller 180 maycontrol a video, which was being reproduced in the unlock state to becontinuously reproduced even in the lock state.

Referring to FIG. 14B, when the lock state is executed while reproducingthe video, the controller 180 may pause the reproduction and display thepaused screen on the lock screen. Then, when the lock state is releasedby receiving a user's touch input via the object 230, the controller 180may restart reproducing of the video based upon the paused screen on thelock screen.

Consequently, the mobile terminal can provide execution informationrelating to an application to the user in the lock state, and controlthose applications on the lock screen.

In the meantime, the touch screen 151 (see FIGS. 1 and 2) having thelock screen displayed thereon may be kept powered on (turned on).Alternatively, the touch screen 151 may be switched into a power-offstate after a preset time elapses in order to reduce power consumptionof a battery and unnecessary power consumption. Also, the power-offstate may be converted into the power-on state again by the user (forexample, by a user's key input).

In the mobile terminal according to the one exemplary embodiment, thetime for which the lock screen is powered on may be set by the user onthe lock screen.

FIGS. 15A and 15B respectively show a method for setting a time forwhich the lock screen is powered on (kept displayed).

First, as shown in FIG. 15A, the controller 180 may display a time, forwhich the lock screen is powered on (kept displayed), using an icon,which has a shape changed as a time elapses. For example, a power-ontime of the lock screen may be displayed using an hourglass icon, aclock icon, or a balloon icon. When the user desires to maintain thepower-on state (displayed state) of the lock screen longer than thedisplayed power-on time, upon inclining the terminal main body within apreset angle, the sensing unit 140 may detect the inclination totransfer to the controller 180, and then the controller 180 may extendthe power-on time based upon the inclination.

For example, in a state that the power-on time of the lock screen is 5minutes left, when the terminal 100 (see FIG. 2) is inclined by about180° and then turned back to its original state, the hourglass icon isfilled with sand again and the power-on time of the lock screen extends20 minutes more.

Also, referring to FIG. 15B, the controller 180 may indicate a time forwhich the lock screen is powered on in form of a bar 280. When the usermoves (scrolls) the bar 280 by virtue of a touch input, the power-ontime of the lock screen may extend.

As described above, the present disclosure allows controlling of thepower-on time of the lock screen even in the lock state, accordingly,the lock screen which displays an execution screen required to the usercan be kept visible.

Meanwhile, the mobile terminal may display a screen, which is capturedin response to a capture command, on the lock screen when the lockscreen is executed in a state that the capture command for anapplication has been generated before executing the lock state.

Herein, the capturing indicates converting a displayed screen into aformat of an image, and the captured screen may be stored in the memory160 (see FIG. 1).

Referring to FIG. 16, when the lock state is started after the usergenerates a command of capturing an execution screen 210 of anapplication, the controller 180 may display the captured screen on thelock screen.

The lock state may be executed by a preset key input (hold key), or asshown, executed by turning the terminal 100 (see FIG. 2) over orobscuring the camera 121 (see FIGS. 2A and 2B) with the terminal turnedover.

As described above, in accordance with a mobile terminal and a controlmethod thereof, an execution screen of an application can be displayedon a lock screen displayed in a lock state, thereby allowingapplication-related information to be provided even in the lock state.

Also, the mobile terminal may be allowed to activate an applicationdisplayed on a lock screen when a touch input for releasing the lockstate is detected on an execution screen of the correspondingapplication, thereby facilitating a user to enter the application.

The configurations and methods of the mobile terminal may not belimitedly applied, but such embodiments may be configured by a selectivecombination of all or part of each embodiment so as to derive manyvariations.

The foregoing embodiments and advantages are merely exemplary and arenot to be construed as limiting the present disclosure. The presentteachings can be readily applied to other types of apparatuses. Thisdescription is intended to be illustrative, and not to limit the scopeof the claims. Many alternatives, modifications, and variations will beapparent to those skilled in the art. The features, structures, methods,and other characteristics of the exemplary embodiments described hereinmay be combined in various ways to obtain additional and/or alternativeexemplary embodiments.

As the present features may be embodied in several forms withoutdeparting from the characteristics thereof, it should also be understoodthat the above-described embodiments are not limited by any of thedetails of the foregoing description, unless otherwise specified, butrather should be construed broadly within its scope as defined in theappended claims, and therefore all changes and modifications that fallwithin the metes and bounds of the claims, or equivalents of such metesand bounds are therefore intended to be embraced by the appended claims.

What is claimed is:
 1. A mobile terminal configured to operate during alocked state and during an unlocked state, the mobile terminalcomprising: a touchscreen; and a controller configured to: execute anavigation application at the mobile terminal during the unlocked state;transition the mobile terminal from the unlocked state to the lockedstate; cause the touchscreen to display a map during the locked state,wherein the map is associated with the navigation application anddepicts a geographical area that includes a current location of themobile terminal; cause the touchscreen to display a location indicatoron the map during the locked state, wherein the location indicatorrepresents on the map the current location of the mobile terminal; causethe touchscreen to change a displayed location of the location indicatoron the map to reflect changes in the current location of the mobileterminal; receive, via the touchscreen, a touch input applied to thetouchscreen during the displaying of the map during the locked state;and execute one of different operations based on the touch input and atouch direction of the touch input, wherein: the controller transitionsthe mobile terminal from the locked state to the unlocked state when thetouch input is applied in a first direction during the displaying of themap during the locked state, wherein displaying the map is maintainedthough the mobile terminal is transitioned from the locked state to theunlocked state, wherein: the controller controls the touchscreen toswitch the map of the navigation application into another executionscreen of another application different from the navigation applicationwhen the touch input is applied in a second direction different from thefirst direction during the locked state, wherein the touch input appliedin the second direction does not release the locked state.
 2. The mobileterminal of claim 1, wherein the controller causes the touchscreen todisplay event data during the locked state in response to an occurrenceof an event, wherein the event data is displayed simultaneously, for aperiod of time, with the displaying of the map, and wherein the eventdata is text associated with a text message received while the mobileterminal is in the locked state.
 3. The mobile terminal of claim 2,wherein the event is a receiving of a text message at the mobileterminal.
 4. The mobile terminal of claim 1, wherein the controller isfurther configured to: transition the mobile terminal from the unlockedstate to the locked state when no user input is received for a thresholdamount of time.
 5. The mobile terminal of claim 1, wherein thecontroller is further configured to: transition the mobile terminal fromthe unlocked state to the locked state in response to a user inputreceived at the mobile terminal.
 6. The mobile terminal of claim 1,wherein during the locked state user input to the navigation applicationis prevented.
 7. The mobile terminal of claim 1, wherein the navigationapplication is a last-displayed user application prior to the transitionfrom the unlocked state to the locked state.
 8. The mobile terminal ofclaim 1, further comprising: a location module configured to receivelocation data; and wherein the controller is further configured to:identify the current location of the mobile terminal using the receivedlocation data.
 9. A method for operating a mobile terminal having atouchscreen during a locked state and during an unlocked state, themethod comprising: executing a navigation application at the mobileterminal during the unlocked state; transitioning the mobile terminalfrom the unlocked state to the locked state; displaying on thetouchscreen a map during the locked state, wherein the map is associatedwith the navigation application and depicts a geographical area thatincludes a current location of the mobile terminal; displaying on thetouchscreen a location indicator on the map during the locked state,wherein the location indicator represents on the map the currentlocation of the mobile terminal; changing a displayed location of thelocation indicator on the map to reflect changes in the current locationof the mobile terminal; receiving, via the touchscreen, a touch inputapplied to the touchscreen during the displaying of the map during thelocked state; and executing one of different operations based on thetouch input and a touch direction of the touch input, wherein: themobile terminal is transitioned from the locked state to the unlockedstate when the touch input is applied in a first direction during thedisplaying of the map during the locked state, wherein displaying themap is maintained though the mobile terminal is transitioned from thelocked state to the unlocked state, wherein: the map of the navigationapplication is switched into another execution screen of anotherapplication different from the navigation application when the touchinput is applied in a second direction different from the firstdirection during the locked state, wherein the touch input applied inthe second direction does not release the locked state.
 10. The methodof claim 9, further comprising: displaying on the touchscreen event dataduring the locked state in response to an occurrence of an event,wherein the event data is displayed simultaneously, for a period oftime, with the displaying of the map, wherein the event data is textassociated with a text message received while the mobile terminal is inthe locked state.
 11. The method of claim 10, wherein the event is areceiving of a text message at the mobile terminal.
 12. The method ofclaim 9, further comprising: transitioning the mobile terminal from theunlocked state to the locked state when no user input is received for athreshold amount of time.
 13. The method of claim 9, further comprising:transitioning the mobile terminal from the unlocked state to the lockedstate in response to a user input received at the mobile terminal. 14.The method of claim 9, wherein during the locked state user input to thenavigation application is prevented.
 15. The method of claim 9, whereinthe navigation application is a last-displayed user application prior tothe transition from the unlocked state to the locked state.
 16. Themethod of claim 9, further comprising: receiving location data; andidentifying the current location of the mobile terminal using thereceived location data.